docs: add changelog entries for PRs #579-#590#614
Conversation
sebbader-sap
requested review from
BirgitBoss,
alexgordtop,
aorzelskiGH,
danielporta,
g1zzm0,
mjacoby,
waltersve and
zrgt
as code owners
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
aaronzi
left a comment
aaronzi
left a comment
There was a problem hiding this comment.
Several changelog entries describe PRs that are still open as of June 5, 2026: #579, #580, #581, #582, #586, and #588. If #614 is merged before those land, the changelog will advertise changes that are not yet in the target branch. Please make sure to merge #614 after those PRs.
All other remarks are inline.
Backports #610, #612, and #613 otherwise match their corresponding original PRs closely, with the expected extra V3.1.3 changelog line.
| Minor Changes: | ||
|
|
||
| * fix: Harmonized `SecurityQueryFilter` between API and Security specifications and added missing `FILTERLIST` construct to the BNF grammar and JSON Schema. | ||
| * fix: Aligned `idShort` pattern in BNF grammar and JSON Schema with Metamodel Constraint AASd-002 to correctly enforce minimum two characters and prevent trailing hyphens. |
There was a problem hiding this comment.
The referenced PR #580 also changes Part2-API-Schemas/openapi.yaml, and its own PR body claims pages/schema.adoc is touched, though the actual #580 diff does not include that file. The related backport #611 does include both OpenAPI and schema.adoc. Please make this changelog entry explicit about the OpenAPI schema update, and double-check whether #580 is missing the generated schema.adoc update.
| * docs: Added normative Query Evaluation Semantics clause to standardize query behavior across implementations, including error handling, field resolution, and list-valued matching. | ||
| * docs: Added normative Operation-to-RIGHT mapping table documenting the correspondence between HTTP/REST API operations and IDTA-01004 rightsEnum values. | ||
| * docs: Added cross-spec terminology matrix reference to align Metamodel classes, API path segments, and Query/Access-Rule prefixes across specifications. | ||
| * docs: Added cross-specification alignment matrix to document API compatibility with IDTA-01001 (Metamodel v3.2) and IDTA-01004 (Security v3.1). |
There was a problem hiding this comment.
PR #588’s actual diff replaces the old dependency/version section with a broader alignment matrix covering IDTA-01001, IDTA-01003-a, IDTA-01003-b, IDTA-01004, and IDTA-01005, including changing IDTA-01005 from v3.1 to v3.2. This entry only mentions IDTA-01001 and IDTA-01004, so it undersells part of the actual changelog impact. Please mention the broader companion-spec alignment, or at least include the IDTA-01005 v3.2 alignment.
3 participants
Changelog Entries for V3.2 PRs
This PR adds changelog entries for PRs #579-#590 targeting the V3.2 release.
Bugfixes (PRs #579-#582)
Documentation Enhancements (PRs #583-#590)
All entries follow the format established in previous changelog entries, focusing on clear descriptions without GitHub issue links (as these are review changes).
Related